Core Web Vitals: Optimizing LCP, INP, and CLS Using Field and Lab Evidence

core-web-vitals is an Agent Skill (v2.0, MIT) in Addy Osmani’s web-quality-skills repository, focused on the three Core Web Vitals: LCP, INP, and CLS. It requires first reviewing CrUX p75 data and browser performance traces, then investigating code and resources only for failing metrics, and retesting with equivalent lab measurements after fixes, without claiming immediate improvements in field metrics. The documentation covers common LCP root causes, checklists, dedicated references for INP/CLS, and the boundaries of measurement sources such as CrUX, Lighthouse, and first-party RUM. Installation: npx skills add specifying the repository and --skill core-web-vitals.

Read More
web-quality-audit: One-Stop Website Quality Audits with Lighthouse

web-quality-audit is an Agent Skill in Addy Osmani's web-quality-skills, centered on Lighthouse 13+ and browser-verified evidence, covering performance (including Core Web Vitals), accessibility, SEO, best practices, and Agentic Browsing. It chains 150+ checks, categorizes them by impact and confidence, provides remediation suggestions, and supports tool routing for Lighthouse CLI, PageSpeed Insights, and Chrome DevTools MCP. After installing it with npx skills add, you can trigger a site-wide or single-page audit using natural language.

Read More
Frontend Performance Audit with web-perf Skill: Integrate Core Web Vitals into Agent Workflow

### Official Cloudflare Agent Skill `web-perf` Introduction This tool leverages Chrome DevTools MCP to audit Core Web Vitals (LCP, INP, CLS) alongside FCP, TBT, and Speed Index, and troubleshoots issues including render-blocking resources, network dependency chains, layout shifts, and caching problems. The article explains its positioning, five-stage workflow, installation methods in tools such as Cursor, Claude Code, and Codex, mandatory configurations for MCP, typical prompt words and output formats, and reminds users to verify thresholds against current official documentation and avoid hardcoding conclusions without an MCP.

Read More